Repository navigation
docs: quick-start: using an existing node key (plain or encrypted, Docker or native) - #174
Merged
Merged
Conversation
…cker or native) A new section 10 for operators who keep an identity they already have: a plain key in the native folder before the set-up, an encrypted key on a console (not under systemd), a plain key in Docker (~/.credits/keys, uid 1000, mode 600; the container makes keys only when keys/NodePublic.txt is missing), and an encrypted key in Docker, converted once with the image's own node --dumpkeys. Also the native conversion for systemd. Troubleshooting becomes section 11. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds section 10 "Using your existing node key" to
docs/quick-start.md(Troubleshooting becomes 11). It covers four cases, each with copy-paste steps:NodePrivate.txtandNodePublic.txtincsnodebeforesetup.sh/setup.bat. The set-up offers the key as the accountnodeand sets mode 600.~/.credits/keys, copy the files in with owner 1000 and mode 600, start, then check withcredits-wallet account node-key. The node does not log its own public key. The container makes new keys only whenkeys/NodePublic.txtis missing (entrypoint.sh line 187).node --dumpkeys, then continue as in case 3. Includes a native variant, for systemd.Warnings: never run two nodes with the same key; keep an offline backup, since a plain key is as exposed as the machine; the wallet opens a plain node key without a password, but on mainnet it still asks you to type
send.Tested
Tested with a throwaway key, never a real one, on
ghcr.io/creditscommunity/credits-node:latest(4.2.532-community.17, build 34022dd):node --encryptkey. The result decodes to 88 bytes.p, Enter, the password and Enter works;Keys dumped to /keyconv/keys.jsonand exits 0;nodebinary. It gives the same identical result.credits-wallet account node-keyinside the running container showed the original address withpublic file ... matches. A cleandocker stopexited 0.Not tested: the Windows PowerShell lines.
🤖 Generated with Claude Code